home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Installation Tools & Overlays 2001 November
/
SGI IRIX Installation Tools & Overlays 2001 November - Disc 3.iso
/
relnotes
/
sysadm_cxfs
/
ch4.z
/
ch4
Wrap
Text File
|
2001-10-10
|
5KB
|
133 lines
- 1 -
4. _K_n_o_w_n__P_r_o_b_l_e_m_s__a_n_d__W_o_r_k_a_r_o_u_n_d_s
+o See the Sysadm Base release notes for more information
about known problems and workarounds in the Sysadm Base
software. See the CXFS release notes for more
information about known problems and workarounds in the
CXFS software.
+o Tasks run from the Tasks menu operate on the item
currently highlighted in the tree view. Highlight the
node, cluster, or filesystem you wish to operate on,
then select the task from the Tasks menu.
+o If the GUI is connected to a given node in the cluster,
it is possible that the GUI cannot know the status of
another node in the cluster. In order for a node to
show the state of another node, CXFS services must be
active on the node to which the GUI is connected. This
is because the state information is exchanged by
daemons that are not running unless CXFS services are
active. If CXFS services are not active on a given
node, then it will report the state of all other nodes
as "Unknown". The node can tell that itself is not
active, and will report a state of "Inactive" for its
own state. If CXFS services are active on a given
node, then that node will correctly report the state of
all the other nodes in the cluster.
If you cannot find out the state of a given node,
restart the GUI and connect to an active node in the
cluster, or start CXFS services on the connected node.
+o The 6.5.10 release allows you convert existing IRIS
FailSafe nodes so that they also apply to CXFS. (The
IRIS FailSafe 2.1 release provides similar
functionality, from CXFS to FailSafe.)
+o Sometimes an cluster or node will have been created or
deleted but it is not displayed correctly in the GUI.
You must log in to the server and use the
/etc/init.d/cluster restart command to clear the
problem condition.
+o When running the GUI in a web browser, you may
encounter OutOfMemoryError errors even if there is
plenty of free memory available on your system. To
increase the amount of memory available to the GUI, use
the Java Plug-in Control Panel to set the "Java Run
Time Parameters" to "-mx40m". This allows the Java
Plug-in to use up to 40 megabytes of memory.
- 2 -
To run the Java Plug-in Control Panel on IRIX, visit
the web page
ffffiiiilllleeee::::////vvvvaaaarrrr////nnnneeeettttssssccccaaaappppeeee////ccccoooommmmmmmmuuuunnnniiiiccccaaaattttoooorrrr////jjjjaaaavvvvaaaapppplllluuuuggggiiiinnnn////jjjjaaaavvvvaaaa////CCCCoooonnnnttttrrrroooollllPPPPaaaannnneeeellll....hhhhttttmmmmllll
On Windows, the Java Plug-in Control Panel is available
on the "Programs" section of the "Start" menu.
You will need to close all of your browser windows and
then restart your browser in order for changes made in
the Java Plug-in Control Panel to take effect.
+o If you load the GUI using Netscape on IRIX and then
switch to another page in Netscape, the CXFS Manager
GUI will not operate correctly. To avoid this problem,
leave the CXFS Manager GUI page up and open a new
Netscape window if you want to view another page.
+o When running the GUI on IRIX, either from the Toolchest
or from a web browser, switching desks using the desks
overview _o_v(1) while a window is coming up can crash
Java.
+o Sometimes when running the GUI from a web browser
windows will ignore input. When this happens move the
window on the screen and it should once again accept
input.
+o When stopping CXFS services on the entire cluster, the
cluster is actually stopped one node at a time to
ensure proper recovery of distributed resources.
Stopping one node can take 1 or 2 minutes, so the
operation can take a while to complete on large
clusters. You can follow its progress in the GUI; the
node icons should switch from green to gray one after
the other.